Skip to content

release: v1.5.0 — daily PyPI poll for newer engine + version realignment#47

Merged
dmartinochoa merged 1 commit into
mainfrom
release/v1.5.0
May 27, 2026
Merged

release: v1.5.0 — daily PyPI poll for newer engine + version realignment#47
dmartinochoa merged 1 commit into
mainfrom
release/v1.5.0

Conversation

@dmartinochoa
Copy link
Copy Markdown
Member

Summary

  • Daily PyPI poll for a newer engine. Once per 24h (per-session latch + per-day globalState timestamp), the extension queries https://pypi.org/pypi/pipeline-check/json after a successful preflight and surfaces a non-blocking notification when PyPI's latest stable is newer than the installed engine. Upgrade in terminal runs the existing upgradeInTerminal flow (terminal opens, command typed, user reviews + Enter — the "no silent pip mutations" invariant holds). Skip this version silences the prompt for that exact version only; later releases re-prompt. New setting pipelineCheck.engineUpdates.checkEnabled (default true) turns the check off entirely.
  • Independent of MIN_ENGINE_VERSION. The hard floor in src/preflight.ts still drives the Upgrade welcome panel when the engine is too old to support the extension's features; the notifier covers the orthogonal "preflight succeeded but newer is available" gap.
  • Version jump 1.1.0 → 1.5.0 to align with upstream pipeline-check engine's 1.5.x line. No skipped functionality between 1.1.0 and 1.5.0; the notifier is the only user-visible change.

Test plan

  • npm run typecheck — clean
  • npm test — 391/391 pass (was 364; +27 new in src/engineUpdates.test.ts covering throttle, fetch success/5xx/network/malformed/missing-impl, and orchestration: disabled/throttled/fetch_failed/no_newer/skipped/prompted×3, persistence on success vs failure, skip-then-newer re-prompts, session latch holds through fetch failure)
  • npm run lint — clean
  • npm run vscode:prepublish — bundle 376.3 KB
  • npm run smokeactivate/deactivate exported, vscode-languageclient bundled
  • npm audit --omit=dev --audit-level=high — 0 vulnerabilities (matches publish gate)
  • Tag v1.5.0 after merge to trigger Marketplace + Open VSX publish

🤖 Generated with Claude Code

Adds a non-blocking notifier that checks PyPI once per day for a newer
`pipeline-check` engine and surfaces an Upgrade prompt when one is
available. Action runs the existing `upgradeInTerminal` flow (terminal
opens, command typed, user reviews and presses Enter) — the "no silent
pip mutations" invariant from src/install.ts holds. Failure paths
(offline, 5xx, malformed JSON, timeout) are silent and logged. New
`pipelineCheck.engineUpdates.checkEnabled` setting (default true)
turns the check off entirely.

Independent of the hard `MIN_ENGINE_VERSION` floor in src/preflight.ts:
the floor still drives the Upgrade welcome panel when the installed
engine is too old to support the extension's features; the new
notifier covers the "preflight succeeded but newer is available" gap.

Version jumps 1.1.0 → 1.5.0 to align the extension stream with the
upstream pipeline-check engine's 1.5.x line so users can read the
two side-by-side. No skipped functionality between 1.1.0 and 1.5.0;
the engine-update notifier is the only user-visible change.

391/391 tests pass (+27 in src/engineUpdates.test.ts), typecheck and
lint clean, prod-only npm audit clean. Bundle smoke OK at 376.3 KB.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

Warning

Review limit reached

@dmartinochoa, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 20 minutes and 34 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 763c586c-8587-4b64-9d55-5d43fb4f80a6

📥 Commits

Reviewing files that changed from the base of the PR and between 6266c40 and ba02c74.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (5)
  • CHANGELOG.md
  • package.json
  • src/engineUpdates.test.ts
  • src/engineUpdates.ts
  • src/extension.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v1.5.0

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@dmartinochoa dmartinochoa merged commit 78aa6c5 into main May 27, 2026
12 checks passed
@dmartinochoa dmartinochoa deleted the release/v1.5.0 branch May 27, 2026 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant